-
Notifications
You must be signed in to change notification settings - Fork 300
chore(ci): add Lazer Sui contract CI #2970
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! We can wait for all the tests to run to be sure.
run: | | ||
set -euo pipefail | ||
CHANNEL="mainnet" | ||
SUI_VERSION="v1.53.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we document that we fix the sui version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(aside) yep it's in the Move.lock file
… Lazer Sui workflow
Documented that the Sui CLI is pinned to the latest stable mainnet (currently mainnet v1.53.2) in the workflow with notes on how to bump and the release/asset naming. CI remains green. |
Summary
Adds a new GitHub Actions CI workflow
ci-lazer-sui-contract.yml
that runs tests for the Pyth Lazer Sui package located atlazer/contracts/sui/
. The workflow installs the Sui CLI and runssui move test
following the same patterns as existing contract CI workflows in the repository.Rationale
The Pyth Lazer Sui package was recently added to the repository and needs automated testing to ensure changes don't break the contract functionality. This CI workflow provides:
How has this been tested?
Testing Notes: This workflow was created by following established patterns from
ci-sui-contract.yml
and other Lazer contract workflows. However, the actual workflow execution has not been manually tested yet. The first PR run will validate that:lazer/contracts/sui/
package structure is compatible withsui move test
Review Checklist
Please pay special attention to:
sui move test
actually works in thelazer/contracts/sui/
directorylazer/contracts/sui/**
lazer/contracts/sui/
is the correct working directoryAdditional Context
Risk factors:
Link to Devin run: https://app.devin.ai/sessions/86899813e8ac45aaa7efbf533e8b9699
Requested by: Tejas Badadare ([email protected])